Understand the difference
Prompts say what to ask. Control layers say what must be true.
Open the visual proof →Open control layers for probabilistic AI
56 Skills.
One control library.
Create, reason, build, verify, and grow with workflows that expose evidence, boundaries, stop conditions, and human authority.
56installable Skills
15public method cards
18public local tools
12copyable fixtures
The product tour
See it. Run it. Inspect it. Decide.
A first visit should feel like a guided product, not an archive. This is the shortest route from a public claim to a checkable result.
Pick one failure
Start before the work, while making the artifact, or before release.
Choose a route →Try a clean install
Use a temporary home and get one bounded result without touching live config.
Run the quickstart →Read the boundary
Match the artifact to its fixture, verifier, evidence, and non-claims.
Inspect the proof →The promise is deliberately narrow: a check proves the contract it names. It does not magically prove model quality, universal compatibility, factual accuracy, or business outcomes.
Start here
Choose the control point.
Do not browse 56 folders first. Start with the moment where an agent most often wastes time: before the work, during creation, or before release.
01
Build the right thing
Turn a vague request into a falsifiable task contract before polished output hides a wrong assumption.
Open Wenzhen demo →02
Make it obvious
Give each page one narrative job, lock one visual grammar, then verify the artifact.
Open Deck demo →03
Catch the failure
Review a change through failure mode, maintenance, and trust-boundary lenses.
Open Reviewer demo →Capability map
The whole system, not a sampler.
Every item installs from this repository. Public beta means source-available, sanitized, package-validated, lifecycle-smoked, and honest about unresolved host-version evidence.
Method layer
Tools reveal capability. Methods reveal judgment.
Fifteen compact rules separate evidence from claims, reversible work from authority, and artifact creation from real-world success.
Proof layer
Inspectable before impressive.
The repository publishes what each check proves—and what it cannot prove. Fluent output is never treated as its own evidence.
45repository unit tests
112/112install matrix passes
112/112offline lifecycle smoke passes
PASSGitHub verify and Pages deployment
Useful control layers should be public.
If one Skill saves you from rebuilding a guardrail, keep the library close.